Service request messaging

ABSTRACT

A method includes receiving a message comprising a user identification code via a social media messaging channel. In addition, the method includes receiving geo-location information of the device transmitting the message. The method also includes verifying the user identification code by confirming that the geo-location information complies with stored expected geo-location information. The method also includes accessing data associated with a transaction account linked to the user identification code based on the content of the message. The method further includes transmitting a reply to the received message on the social media messaging channel.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, claims priority to and thebenefit of, U.S. Ser. No. 15/410,529 filed Jan. 19, 2017 and entitled“SERVICE REQUEST MESSAGING,” which is a continuation of, claims priorityto and the benefit of, U.S. Ser. No. 13/621,941 filed Sep. 18, 2012,U.S. Pat. No. 9,607,344 issued Mar. 28, 2017, and entitled “METHOD,SYSTEM, AND COMPUTER PROGRAM PRODUCT FOR MERCHANT SERVICING,” both ofwhich are incorporated herein in their entireties by reference.

FIELD OF DISCLOSURE

The present disclosure generally relates to electronic communications.More particularly, the disclosure relates to methods, systems, andcomputer readable mediums for merchant servicing.

BACKGROUND

Industries, corporates, and/or institutions (herein referred to as“institutions”) may have merchants and/or service providers (hereinreferred to as “merchants”) for providing services to the institutions.The institutions and the merchants may agree through a contract toprovide bi-lateral services for customers of the institution for aperiod stated in the contract. For example, financial institutions(e.g., banks) may offer the merchants a contract for servicing customershaving transaction accounts in the aforesaid banks. The merchantsprovide services to customers of the institutions by offering productsand/or services in return for considerations from the institution. Thecustomers may perform transactions with the merchants using thetransaction accounts, for goods and services. The institutions on behalfof the customers may provide considerations to the merchants via, forexample, merchant accounts. The merchant accounts are transactionaccounts associated with the merchants. The merchant accounts may beprovided to the merchants by the institutions. The institutions mayprovide services to the merchants in connection with the merchantaccounts. The services may be termed as merchant servicing. The merchantservicing may include providing information associated with the customertransactions with the merchants, transactions with the institutions,and/or information relating to the merchant accounts. The institutionsmay provide services to the merchant by providing monthly accountstatements, transaction data online on the institution's website and/orinformation through customer care via helpline telephone numbers. Theexisting merchant servicing is insufficient to service the merchants.

It would therefore be desirable to provide a method, system andapparatus that enables merchant servicing through social media messagingchannels.

SUMMARY OF THE DISCLOSURE

The present disclosure improves upon existing systems and methods byproviding a tool for leveraging social media messaging. In variousembodiments, the system is configured to receive a message comprising auser identification code via a social media messaging channel. Thesocial media messaging channel may be a secure media messaging channel.For instance, the social media messaging channel may comprise at leastone of text message, instant message and computer-supportedcollaboration work, servicing request message, MIME email message,multimedia messaging service message, and/or short messaging servicemessage.

Additionally, the system is configured to receive geo-locationinformation of the device transmitting the message. In variousembodiments, the system may verify user identification code by verifyingthat the geo-location information matches stored expected geo-locationinformation. The system may be configured to access data associated witha transaction account linked to the user identification code based onthe content of the message and transmit a reply to the received messageon the social media messaging channel.

In various embodiments, the system may be configured to receiveenrollment information for use of the computer-based system, wherein theenrollment information comprises a merchant identifier and a transactionaccount code. This enrollment information may be merchant log onenrollment information. The transaction account may be a merchanttransaction account. Also, in various embodiments, the system may beconfigured to transmit a second reply to the message on a second socialmedia messaging channel in response to receiving an error messageassociated with the transmitted reply on the social media messagingchannel. The system may be configured to transmit the second reply tothe message on a non-social media messaging channel in response toreceiving an error message associated with the transmitted reply on thesocial media messaging channel. In various embodiments, the system maybe configured to identify the transaction account based on both the useridentification code and the geo-location information used incombination.

In various embodiments, the system may be configured to receive devicetype information of the device transmitting the message. The system maybe configured to identify the transaction account based on one or moreof the user identification code, the geo-location information and/or thedevice type information used in combination. Also, the system may beconfigured to verify the transaction account based on one or more of theuser identification code, the geo-location information and/or the devicetype information used in combination. The system may poll the socialmedia messaging platform for new messages according to a predeterminedperiodic schedule.

Also, in various embodiments, the system may be configured to verify theuser via the geo-location information. The message may be a queryrelated to at least one of a disputed transaction, a pending settlement,a transaction status, a chargeback, and reconciliation.

The system may be configured to transmit a request for additionalinformation in response to the geo-location information not matchingstored expected geo-location information. This (computer-based) systemmay be administered by, used by, and/or implemented by a transactionprocessor. The data associated with a transaction account may be relatedto a specifically identified transaction. Moreover, the reply to thereceived message may comprise data relating to a selected range oftransactions.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present disclosure will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference numbers indicateidentical or functionally similar elements. Additionally, the left-mostdigit of a reference number identifies the drawing in which thereference number first appears.

FIG. 1 is an overview of an exemplary environment in which a merchantservice system may be deployed, in accordance with various embodiments;

FIG. 2 is a flow chart illustrating communication between a user deviceand the merchant service system, in accordance with various embodiments;

FIG. 3 is a user interface view illustrating merchant servicing througha social media messaging channel, in accordance with variousembodiments;

FIG. 4 is a process flow illustrating merchant servicing, in accordancewith various embodiments; and

FIG. 5 illustrates a block diagram of an exemplary computer system forimplementing the present disclosure, in accordance with variousembodiments.

DETAILED DESCRIPTION

The present disclosure relates to method, system, and an article ofmanufacture for merchant servicing. Merchant servicing may includeproviding information associated with a transaction account of amerchant. The information may include recent transactions, disputestatuses, reconciliation information, net account balance, and the like.In various embodiments, merchant servicing may be enabled using amerchant servicing system (MSS). The MSS may provide merchant servicingthrough one or more secure social media messaging channels. Social mediamay include web- and mobile-based technologies which are used to turncommunication into interactive dialogue among organizations,communities, and individuals. Social media technologies take on manydifferent forms including magazines, Internet forums, weblogs, socialblogs, micro blogging, wilds, social networks, podcasts, photographs orpictures, video, rating and social bookmarking. The MSS may receive amessage from a merchant through the one or more social media messagingchannels. The MSS, in response to the message, may communicateinformation associated with the merchant account to the merchant throughthe one and/or more social media messaging channels, or non-social mediamessaging channels. The social media messaging channels may include atext message, an instant message and computer-supported collaborationwork, a servicing request message, MIME email, and the like. Forexample, the MSS may service the merchant using messaging channelsprovided by various social media platforms such as Twitter®, Facebook®,MySpace® and the like. Thus, the MSS may leverage social media messagingchannels to provide services to the merchants.

The term “user”, “merchant” and “vendor” are used interchangeablyherein. A “merchant” is any entity that provides items in return for aconsideration. For example, a merchant may be a retail store, a travelagency, a restaurant, a hotel, a service provider, an on-line merchant,and the like. The merchant may be associated with a financialinstitution through a transaction account (merchant transactionaccount).

Phrases and terms similar to an “item” may include any good, service,information, experience, data, content, access, rental, lease,contribution, account, credit, debit, benefit, right, reward, points,coupons, credits, monetary equivalent, anything of value, something ofminimal or no value, monetary value, non-monetary value and/or the like.

FIG. 1 shows an exemplary network environment 100, in which variousembodiments of the present disclosure may be deployed. As shown in theFIG. 1, exemplary network environment 100 includes a merchant servicesystem (MSS) 102 and a user device 104. Network environment 100 alsoincludes one or more social media servers 106 _(1-N) and a positioningdevice 108. MSS 102, user device 104, social media servers 106 _(1-N),and positioning device 108 may communicate over a network 110.

MSS 102 provides services to a user through one or more social mediamessaging channels. The services may include providing information suchas recent transactions, dispute statuses, reconciliation information,net account balance, transaction updates, and the like, that areassociated with a transaction account (merchant account) of the user. Invarious embodiments, MSS 102 may provide services in response to amessage from the user. In various embodiments, MSS 102 may provideservices without needing a message from the user. The social mediamessaging channel may include, for example, a text messaging channel,instant messaging channel and computer-supported collaboration work, aMIME email messaging channel, multimedia messaging service message,short messaging service message and/or any other existing or developedchannels. The social media messaging channels are enabled through one ormore social media servers 106 _(1-N.) Although the disclosure discussesabout MSS 102 providing services through the one or more social mediamessaging channels, MSS 102 can also provide the services throughnon-social media messaging channels. MSS 102 may provide the services tothe user upon enrollment with MSS 102. In various embodiments, MSS 102may provide the services without the need for the (or only partial) userenrollment. MSS 102 may be managed by a financial institution (notshown) and/or a third-party (not shown) associated with the financialinstitution.

MSS 102 may include a receiving unit 114, a processing unit 116, anextraction unit 118, and a transmission unit 120. Receiving unit 114obtains/receives a new message, such as a message associated with themerchant account communicated by the user to the financial institutionthrough one or more social media servers 106 _(1-N). In variousembodiments, receiving unit 114 polls one or more social media servers106 _(1-N) for new messages communicated by the user. In one exampleimplementation, receiving unit 114 may poll one or more social mediaservers 106 _(1-N) according to a predetermined schedule. In anotherexample implementation, receiving unit 114 may poll one or more socialmedia servers 106 _(1-N) non-periodically. Receiving unit 114 may obtainthe new message in response to identifying the new message in one ormore social media servers 106 _(1-N). In various embodiments, receivingunit 114 may obtain the message upon listening to availability of newmessages in one or more social media servers 106 _(1-N). In variousembodiments, receiving unit 114 may receive the new message communicatedby one or more social media servers 106 _(1-N). Other techniques toreceive a new message from one or more social media servers 106 _(1-N)are contemplated herein. The message received may be an enrollmentmessage or a service request message. The enrollment message may includea request for enrollment, a merchant identifier, and a transactionaccount code. The enrollment message may also include positioninformation in a hierarchy, user device information, geo-locationinformation, information required for the position if enrolled, and/orthe like. The service request message may include transaction accountdetails, user identification codes, request for service associated withthe transaction account, device type information, geo-locationinformation associated with the transaction account, among others.Receiving unit 114 may receive geo-location of user device 104 and userdevice type information from the message itself. In some embodiments,receiving unit 114 may receive geo-location of user device 104 and userdevice type information from one or more social media servers 106_(1-N). Although, the disclosure discusses receiving the message throughone or more social media messaging channels, receiving unit 114 can alsoreceive the message directly from the user through non-social mediamessaging channels. Receiving unit 114 may communicate the message toprocessing unit 116.

Processing unit 116 processes the message to determine whether themessage is an enrollment message or a service request message. If themessage is an enrollment message, processing unit 116 may determinewhether the message includes a user identifier and a transaction accountcode. Processing unit 116 may compare the user identifier andtransaction account code with the user identifier information andtransaction account code, respectively in database 112. In response tosuccessful comparison, processing unit 116 may enroll the user.Otherwise, processing unit 116 may generate an error message to becommunicated to the user. Additionally, processing unit 116 may alsoprocess additional data such as hierarchy information, position inhierarchy information, and services required according to the positionprovided in the message (if any). Processing unit 116 may set hierarchy,positions in the hierarchy and services required for corresponding tothe positions, based on hierarchy information, positions in hierarchy,services required for the positions in hierarchy, respectively, obtainedfrom the message.

If the message is a service request message, processing unit 116 mayverify the user identification code, the user, the geo-locationinformation of the user, service required and the like. Processing unit116 may verify the user identification code in the message by confirmingthat the geo-location information complies with stored expectedgeo-location information. The expected geo-location information may bestored in database 112. In response to the geo-location information notcomplying with the stored expected geo-location information, processingunit 116 may generate a request for additional information. The requestis communicated to the user through transmission unit 120. In responseto the geo-location information complying with the stored expectedgeo-location information, processing unit 116 may identify that the userinformation code belongs to the user. Processing unit 116 also verifiesand identifies the user via the geo-location information. Processingunit 116 may verify the transaction account of the user based on theuser identification code, the geo-location information and/or the devicetype information. Additionally, processing unit 116 may determinehierarchy information based on the user identification code, if any.Processing unit 116 may determine service requested by user based onservice request in message and/or hierarchy information (if any).Processing unit 116 may communicate one or more requests to extractionunit 118 to extract information from database 112, to provide theservice. The information may include one or more of transaction data,dispute statuses, reconciliation information, account status, balance inaccount, and the like.

Extraction unit 118 extracts information associated with transactionaccount from database 112, based on service request. In someembodiments, extraction unit 118 may extract information relevant togeo-location of the user and/or position of the user in the hierarchy.Consider an example; the user may have two apparel stores, one inHouston and other in New York. If the user communicates a message fortransaction information through a user device from Houston location,extraction unit 118, based on geo-location (Houston) may extracttransaction information relevant to the user's store in Houstonlocation. For instance, expected geo-location information may begeo-location information in close proximity to a merchant's storefront,for instance, in this case the Houston area.

If the user communicates a message for transaction information through auser device from the New York location, extraction unit 118, based ongeo-location (New York) may extract transaction information relevant tothe user's store in New York location.

If the user communicates a message for transaction information through auser device from a location other than Houston or New York, extractionunit 118, based on geo-location may request additional information priorto proceeding with information extraction and/or transmission.

In another example, there may be multiple level users for the apparelstores described above. If a level one user requests for transactiondata, extraction unit 118 may extract hourly transaction data for thestores. Extraction unit 118 may not extract weekly transaction data forthe level one user, as extraction unit 118 is not authorized to provideweekly transaction data to the level one user. The authorization forservices may be set by the user in the MSS 102. In yet another example,the level one user of Houston stores may message for the transactiondetails, extraction unit 118 may extract hourly transaction detailsassociated with Houston store and appropriate for the level one user.

Transmission unit 120 may communicate the extracted information to userdevice 104 as a reply to the message. Transmission unit 120 maycommunicate the reply to user device 104 through one or more socialmedia messaging channels, one or more non-social media messagingchannels or both. Although, above description describes about MSS 102processing a single message, it can be appreciated that MSS 102 canprocess multiple messages as well.

User device 104 as discussed herein may be any device capable oftransmitting and receiving messages through one or more social mediamessaging channels or non-social media messaging channels or both.Examples of user device 104 may include, without limitation, personalcomputers, Cellular communication devices, Hand-Held display devices,smartphones, personal digital assistants (PDAs), and the like. Invarious embodiments, user device 104 may include a social mediamessaging client installed thereon. The user may compose and communicatethe message through the social media messaging client. In some exampleimplementations, social media messaging client may be capable ofautomatically including, for example, the user identification code,transaction account code, geo-location of user device 104, and the like,to the message. In various embodiments, the user may include one or moreof the user identification code, transaction account code, request forservice, geo-location of user device 104, service request, position inhierarchy information and/or the like. In various embodiments, userdevice 104 may not include any social media messaging client. In suchcases, the user may have to compose the message including the useridentification code, the transaction account code, geo-location of userdevice 104, service request, position in hierarchy information (if any),and the like. User device 104 may include suitable hardware and/orsoftware for communicating with MSS 102 and/or one or more social mediaservers 106 _(1-N) through network 110. In various embodiments, userdevice 104 may be electrically coupled to a positioning device 108. Userdevice 104 may obtain geometrical co-ordinates of user device 104through positioning device 108.

Positioning device 108 may be a Global Positioning Satellite (GPS)device for determining geometrical co-ordinates of user device 104. Invarious embodiments, other technologies, such as global packet radioservice (GPRS), Internet Protocol address, may be used to determinegeo-location of user device 104.

Social media servers 106 _(1-N) may include one or more of a textmessage server, an instant messaging server, a computer-supportedcollaboration work server, an email server, a multimedia messagingservice message, a short messaging service server, and/or any socialnetworking servers for such as Facebook® and Twitter®. Social mediaservers 106 _(1-N) may host and implement secure social media messagingchannels through which the user and MSS 102 communicate with each other.

In various embodiments, components, modules, and/or engines of system100 may be implemented as micro-applications or micro-apps. Micro-appsare typically deployed in the context of a mobile operating system,including for example, a Palm mobile operating system, a Windows mobileoperating system, an Android Operating System, Apple iOS, a Blackberryoperating system and the like. The micro-app may be configured toleverage the resources of the larger operating system and associatedhardware via a set of predetermined rules which govern the operations ofvarious operating systems and hardware resources. For example, where amicro-app desires to communicate with a device or network other than themobile device or mobile operating system, the micro-app may leverage thecommunication protocol of the operating system and associated devicehardware under the predetermined rules of the mobile operating system.Moreover, where the micro-app desires an input from a user, themicro-app may be configured to request a response from the operatingsystem which monitors various hardware components and then communicatesa detected input from the hardware to the micro-app.

As used herein, the term “network” (e.g., network 110) includes anycloud, cloud computing system or electronic communications system ormethod which incorporates hardware and/or software components. It shouldbe appreciated that other types of networks are also contemplatedherein. Data communication between user device 104, social media servers106 _(1-N), MSS 102, and positioning device 108 may occur over network110 through social media messaging channels, in an encrypted orotherwise secure format, in any of a wide variety of known manners.Communication among the parties may be accomplished through any suitablecommunication channels, such as, for example, a telephone network, anextranet, an intranet, Internet, point of interaction device (point ofsale device, personal digital assistant (e.g., iPhone®, Palm Pilot®,Blackberry®), cellular phone, kiosk, etc.), online communications,satellite communications, off-line communications, wirelesscommunications, transponder communications, local area network (LAN),wide area network (WAN), virtual private network (VPN), networked orlinked devices, keyboard, mouse and/or any suitable communication ordata input modality. Moreover, although the system is frequentlydescribed herein as being implemented with TCP/IP communicationsprotocols, the system may also be implemented using IPX, Appletalk,IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or anynumber of existing or future protocols. If the network is in the natureof a public network, such as the Internet, it may be advantageous topresume the network to be insecure and open to eavesdroppers. Specificinformation related to the protocols, standards, and applicationsoftware utilized in connection with the Internet is generally known tothose skilled in the art and, as such, need not be detailed herein. See,for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (1998); JAVA 2COMPLETE, various authors, (Sybex 1999); DEBORAH RAY AND ERIC RAY,MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IP CLEARLY EXPLAINED (1997)and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (2002),the contents of which are hereby incorporated by reference.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish networks, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety.

The system contemplates uses in association with web services, utilitycomputing, pervasive and individualized computing, security and identitysolutions, autonomic computing, cloud computing, commodity computing,mobility and wireless solutions, open source, biometrics, grid computingand/or mesh computing.

Database 112 may employ any type of database, such as relational,hierarchical, graphical, object-oriented, and/or other databaseconfigurations. Common database products that may be used to implementthe databases include DB2 by IBM (White Plains, N.Y.), various databaseproducts available from Oracle Corporation (Redwood Shores, Calif.),Microsoft Access or Microsoft SQL Server by Microsoft Corporation(Redmond, Wash.), or any other suitable database product. Moreover, thedatabases may be organized in any suitable manner, for example, as datatables or lookup tables. Each record may be a single file, a series offiles, a linked series of data fields or any other data structure.Association of certain data may be accomplished through any desired dataassociation technique such as those known or practiced in the art. Forexample, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, using akey field in the tables to speed searches, sequential searches throughall the tables and files, sorting records in the file according to aknown order to simplify lookup, and/or the like. The association stepmay be accomplished by a database merge function, for example, using a“key field” in pre-selected databases or data sectors.

The data set annotation may also be used for other types of statusinformation as well as various other purposes. For example, the data setannotation may include security information establishing access levels.The access levels may, for example, be configured to permit only certainindividuals, levels of employees, companies, or other entities to accessdata sets, or to permit access to specific data sets based on thetransaction, merchant, issuer, consumer, customer or the like.Furthermore, the security information may restrict/permit only certainactions such as accessing, modifying, and/or deleting data sets. In oneexample, the data set annotation indicates that only the data set owneror the user are permitted to delete a data set, various identified usersmay be permitted to access the data set for reading, and others arealtogether excluded from accessing the data set. However, other accessrestriction parameters may also be used allowing various entities toaccess a data set with various permission levels as appropriate. Thedata, including the header or trailer may be received by a stand-aloneinteraction device configured to add, delete, modify, or augment thedata in accordance with the header or trailer. The header may be contentof a message. Free text entry may be content of a message. As such, invarious embodiments, the header or trailer is not stored on thetransaction device along with the associated issuer-owned data butinstead the appropriate action may be taken by providing to thetransaction instrument user at the stand-alone device, the appropriateoption for the action to be taken. Database 112 described hereincontemplates a data storage arrangement wherein the header or trailer,or header or trailer history, of the data is stored on the transactioninstrument in relation to the appropriate data. One skilled in the artwill also appreciate that, for security reasons, any databases, systems,devices, servers or other components of database 112 described hereinmay consist of any combination thereof at a single location or atmultiple locations, wherein each database or system includes any ofvarious suitable security features, such as firewalls, access codes,encryption, decryption, compression, decompression, and/or the like.

Database 112 may include pre-stored information related to profilecharacteristics and financial characteristics of various users. Theprofile characteristics may include information related to parameterssuch as merchant identifiers, transaction account codes, storedgeo-location information of different merchants, user identificationcodes of the merchants, and the like. The financial characteristics mayinclude information related to parameters such as transaction records,merchant account hierarchies, account numbers, pending settlementdetails and the like. Although, database 112 is shown external to MSS102, database 112 may implemented internal to MSS 102. Further, theprofile characteristics and the financial characteristics may also bestored in an internal memory of MSS 102.

FIG. 2 illustrates a flow diagram 200 illustrating communication betweenuser device 104 and MSS 102. MSS 102 may communicate with, for example,a social media server 106 ₁ for obtaining/receiving a new messageaddressed to MSS 102. Social media server 106 ₁ may receive the messagefrom user device 104 via network 110. The message may be communicatedfrom user device 104 to social media server 106 ₁ via a social mediamessaging channel such as a text messaging channel, an instant messagingchannel, an email channel, a computer-supported collaboration work, aservicing request message, a MIME email message, a multimedia messagingservice message, a short messaging service message, or the like. In anexample, the messages may be sent using a direct messaging serviceprovided by Twitter®. In another example, the messages may becommunicated to MSS 102 through short messaging service message. In yetanother example, the messages may be sent using an Instant Messaging(IM) service.

According to step S1 of FIG. 2, social medial server 106 ₁ may receive amessage. The message may be an enrollment message. In an example, theenrollment message may include a user identifier, a transaction accountcode and request for enrollment. A merchant identifier may be a uniquecode or serial number identifying the user. The transaction account codemay be a code identifying a transaction account of the user. Theenrollment message may also include geo-location and device typeinformation of user device 104. The device type information may be anidentifier identifying user device 104. Examples of the deviceinformation may include, without limitation, mobile number, internetprotocol (IP) address, Media Control Access (MAC) address, InternationalMobile Equipment Identity (IMEI) code, International mobile subscriberidentity (ISMI), device ciphering information. The enrollment messagemay be composed using a social media messaging client installed on userdevice 104 or without any social media messaging client. In variousembodiments, the enrollment message may be composed in a specific formatas defined by MSS 102. For example, the enrollment message may becomposed in a following format:

#enrol merc ID nnnn dev ID   (1)

The enrollment message may comprise of a header for identifying a typeof message. As seen in (1), the header is #enrol. Thus, it may beimplied that the type of message is an enrollment message. Further, theenrollment message may include a user (merchant) identifier (“merc ID”),a transaction account code (“nnnn”) and a device ID (“dev ID”). Invarious embodiments, the message can be composed without any format andMSS 102 may process the message.

In step S2, MSS 102 may obtain/receive the new message from social mediaservers 106 ₁. MSS 102 may also obtain a current geo-location of userdevice 104. In various embodiments, MSS 102 may obtain the geo-locationinformation of user device 104 from social media server 106 ₁. Invarious embodiments, MSS 102 may obtain geo-location information of userdevice 104 directly from the message or user device 104. In variousembodiments, MSS 102 may receive geo-location from positioning device108 communicatively coupled to user device 104. MSS 102 may compare theobtained geo-location with geo-location of user device 104 as stored indatabase 112 to determine whether the geo-location of user device 104matches the geo-location stored in database 112. In response tosuccessful comparison, MSS 102 may authenticate the user identificationcode, and the user using the geo-location information.

In step S3, MSS 102 may verify the transaction account code, based onthe verification details obtained from database 112. The verificationdetails may comprise of merchant characteristic data such as transactionaccount information, a merchant identifier, and geo-locations ofmerchant centers, pre-stored in database 112. In response to successfulcomparison, MSS 102 may authenticate the transaction account code.Furthermore, if message includes additional information such asorganizational details, hierarchy information, position of the user inhierarchy and information required for the position, MSS 102 may sethierarchy for user organization, position of the user in the hierarchy,and default information to be communicated to user in case of messagefrom the user without specific request. MSS 102 may communicate asuccessful enrollment notification as a reply to the enrollment messageto user device 104 through social media server 106 ₁ as depicted in stepS4. If the authentication of the user identification code and/or thetransaction account code fails, MSS 102 may communicate an errornotification to user device 104. In addition, MSS 102 may ask foradditional details from the user.

In step S5, social media server 106 ₁ may receive a new message fromuser device 104 addressed to MSS 102. The message may be receivedthrough a social media messaging channel, such as a text messagingchannel, MIME e-mail channel, and instant messaging channel, and thelike. The message may be a service request message. In step S6, MSS 102may obtain the message addressed to MSS 102 through, for example,polling. The message may include user identification code, transactionaccount information, a service request for information associated withthe transaction account, device type information (optional),geo-location information (optional) and position in hierarchyinformation (if any). The information associated with the transactionaccount may include recent payments, dispute statuses, pendingsettlements, reconciliation information, and/or the like. In variousembodiments, the service request message may be in a fixed format. Forexample, the message format for the service request message may be asfollows:

MYPAY nnnn mm/dd/yyyy mm/dd/yyyy UID   (2)

According to (2), the header of the transaction query message is“MYPAY”, standing for “My Payment”. A listing of headers and the resultsthey obtain may be communicated to the user at any time, for instance,in response to an incorrect or unknown header being received. Thetransaction query may further include the last four digits (“nnnn”) ofthe transaction account of the user, the two dates between which thetransaction details are required, and the user identification code ofthe user. The date format, as depicted in (2), is an “mm/dd/yyyy”format, however other date formats may also be used. In variousembodiments, the message may be in a format free text that may beprocessed by MSS 102.

MSS 102 may process the message to verify the user identification codeof the user. MSS 102 may verify the user identification code byconfirming that the geo-location information complies with storedexpected geo-location information. The geo-location information of userdevice 104 may be obtained as previously described. If the useridentification code authentication fails, MSS 102 may transmit an errormessage such as “incorrect user identification code” notification backto user device 104. Otherwise, MSS 102 may verify the transactionaccount of the user based on user identification code, the geo-locationinformation, and/or device type information. In response to successfulverification, MSS 102 may identify the service request in the message.Based on the service request, MSS 102, in step S7, may extractinformation associated with the transaction account from database 112.For example, if a user requests for transaction details betweenparticular dates through the message, MSS 102 may extract thetransaction details such as amount of deposits, date of deposits andlocations of deposits of those dates from database 112. Additionally, ifthe message includes hierarchy information, MSS 102 may evaluate whetherthere is an authorization to provide service requested. If MSS 102determines that there is authorization to provide service requested forthe position in hierarchy, MSS 102 may extract information based on theservice requested in accordance to the position of the user inhierarchy. Otherwise, MSS 102 may generate an error message.

In various embodiments, an account hierarchy may also be stored withindatabase 112. The account hierarchy may depict relationship betweenmultiple transaction accounts held by a single user. MSS 102 may extracttransaction details from database 112 based on the account hierarchy.For example, if a transaction query message includes a transaction queryfor retrieving payment details related to a parent account held by amerchant, MSS 102 may also extract payment details related to all otheraccounts that have a hierarchical relationship with the parent account.

In step S8, MSS 102 may provide the service requested through socialmedia server 106 ₁. Referring to the above stated example of a usersending a transaction query message for retrieving information relatedto payments, MSS 102 may provide the transaction details in a followingformat for dates between Oct. 10, 2010 and Oct. 13, 2010:

TABLE 1 Transaction Details Transaction Amount of Type of Location ofDate Transaction Transaction Transaction Oct. 10, 2010 $433.54 CreditAustin, Texas City Oct. 10, 2010 $200.00 Credit Houston Oct. 13, 2010$120.50 Negotiable Manhattan instrumentIn the above table, transactions for the dates are provided forillustration purposes only.

In step S8, MSS 102 may communicate the information as a reply to themessage via social media server 106 ₁ through the social media messagingchannel. For example, if the user communicates the message to MSS 102using a messaging service provided by Twitter®, MSS 102 may communicatethe reply in response to message using the same messaging service(Twitter®). Social media server 106 ₁ may receive the reply. In step S9,social media server 106 ₁ may transmit the reply to the user. The usermay receive the reply in user device 104.

In various embodiments, MSS 102 may communicate the reply through one ormore social media messaging channels other than the social mediamessaging channel used by the user. MSS 102 may communicate the replythrough another social media messaging channel responsive to a receivingerror message while communicating the reply through the social mediamessaging channel used by the user. The error message may be receiveddue to a failure in communication of the reply due to various technicalerrors such as network congestion, server downtime, channel maintenance,and the like. In various embodiments, MSS 102 may communicate the replyto the user using a non-social media messaging channel such as throughdirect e-mail. Alternate channels for information communications and thehierarchy/preferred order of their use may be predefined by the user.

In various embodiments, in response to receiving a communication from avalidated user, such as a prior user, MSS 102 may communicate replycomprising the type of prior requested information. In this way, arepeat user does not have to include the full request message includingheader information to MSS 102 in subsequent communications.

Although, FIG. 2 illustrates a step of enrollment before communicatingthe message for service, one can appreciate that MSS 102 can alsoprovide services to messages without a requirement of the user enrollingwith MSS 102 as database 112 may include user information that can beused to verify the credentials of the user through social mediamessaging channels.

FIG. 3 is a user interface view illustrating merchant servicing throughsocial media messaging channel. A user may have an account registeredwith a social media messaging channel provider. As illustrated in FIG.3, the user (Stephen Johns) has a registered social media messagingusemame “@Stephen.J” with a social media messaging channel provider. Theuser may login to the registered account using the registered socialmessaging usemame through a user device 302. The user may compose anenrollment message M1 addressed to MSS (not shown) using a messaginginterface of the social media messaging channel. As illustrated in FIG.3, the user may compose the message in the format “#enrol SJ0001234555123456772”. The header #enrol indicates request for enrollment. Theportion “SJ00012345” indicates a merchant identifier. The portion“55123456772” indicates a transaction account code. The user maycommunicate the enrollment message to the MSS through a social mediamessaging channel (using send button).

In response to receiving the enrollment message M1 and successfulenrollment, MSS may communicate a reply M2 to user device 302. The replyM2 as illustrated indicates a “successful enrollment” notification. Inthe current example, the reply M2 includes the user identification codeof the user. As depicted in FIG. 3, the successful enrollment messagemay be displayed as “Enrollment successful UID: SJ090654TX”. The UID maybe the user identification code of the user to be used for furthercommunications with the MSS.

Once the reply M2, i.e. “successful enrollment” notification, isreceived by the user, the user may compose the transaction query messageon the messaging interface 304. The transaction query message M3 may becomposed by the user in a pre-defined message format. As depicted in anexample in FIG. 3, the user may compose a service request message M3 as:“MYPAY AMT 1365 Nov. 10, 2010 Nov. 15, 2010 SJ090654TX”. Referring tothe format of transaction query message M3, the message body may includea header identifying type of transaction parameter queried about. Asillustrated, the header “MYPAY AMT” may indicate that the servicerequest is associated with “amount of payments deposited”. The messagebody may further include the last four digits of the user's transactionaccount number (1365) and the dates between which the user has requesteddetails of transactions associated with the user's transaction account.The dates are followed by the user identification code (SJ090654TX).Once the transaction query message is composed in a pre-defined format,the user communicates service request message M3.

In response to receiving service request message M3, the MSS may performvalidations on the service request message M3. In response to validationof the service request message M3, MSS 102 may communicate transactioninformation associated amount of payments deposited in the usertransaction account between Oct. 11, 2010 and Oct. 12, 2010. Thetransaction information may be communicated in a form of message M4. Asdepicted, the transaction detail message M4 may be displayed as aresponse to the transaction query message M3. As depicted, amounts$433.54 and $200 have been credited to the user's transaction account on11^(th) Oct. 2010. Further, an amount of $120.50 has been deposited touser's transaction account on 12^(th) Oct. 2010 through a negotiableinstrument.

FIG. 4 illustrates a process flow 400 for merchant servicing. Theprocess may begin at step S402 where MSS 102 receives a messagecomprising a user identification code via a social media messagingchannel. The social media messaging channel may comprise text message,instant message and computer-supported collaboration work, MIME e-mailmessage, multimedia messaging service, short messaging service, and thelike. The social media messaging channel may be enabled by one or moresocial media servers 106 _(1-N). In one example, MSS 102 may receive themessage through one or more social media servers 106 _(1-N).

At step S404, MSS 102 receives geo-location information of user device104. In various embodiments, MSS 102 may receive the geo-locationinformation of user device 104 from the message or user device 104. Invarious embodiments, MSS 102 may receive geo-location information ofuser device 104 from one or more social media servers 106 _(1-N). Atstep S406, MSS 102 verifies the user identification code of the userobtained from user device 104. MSS 102 may verify the useridentification code by confirming that the geo-location informationobtained complies with the geo-location information stored in database112.

At step S408, MSS 102 accesses data associated with the transactionaccount linked with the user identification code based on the content ofthe message. The data associated with the transaction account of theuser may be stored in database 112. The data associated with thetransaction account of the user may include transaction details such asdetails associated with a disputed transaction, a pending settlement, atransaction status, a chargeback, and reconciliation, and/or the like.The data associated with the transaction account of the user may beaccessed from database 112. The data associated with the transactionaccount of the user may be accessed based on the content of the message.For example, if the message content is for retrieving last five paymentsthen data related to the last five payments such as amount of payment,mode of payment, date of payment, location of payment, and the like, maybe extracted from database 112. At step S410, MSS 102 transmits a replyto the received message on the social media messaging channel. The replymay be transmitted to user device 104 through one or more social mediaserver 106 _(1-N). The reply may include the data related to the lastfive payments associated with the transaction account.

The present disclosure (i.e., system 100, system 200, process 400,system 400, process 500, or any part(s) or function(s) thereof) may beimplemented using hardware, software or a combination thereof, and maybe implemented in one or more computer systems or other processingsystems. However, the manipulations performed by the present disclosurewere often referred to in terms, such as comparing or checking, whichare commonly associated with mental operations performed by a humanoperator. No such capability of a human operator is necessary, ordesirable in most cases, in any of the operations described herein,which form a part of the present disclosure. Rather, the operations aremachine operations. Useful machines for performing the operations in thepresent disclosure may include general-purpose digital computers orsimilar devices.

In fact, in accordance with various embodiments of the presentdisclosure, the present disclosure is directed towards one or morecomputer systems capable of carrying out the functionality describedherein. An example of the computer systems includes a computer system500, which is shown in FIG. 5.

The computer system 500 includes at least one processor, such as aprocessor 502. Processor 502 is connected to a communicationinfrastructure 504, for example, a communications bus, a cross over bar,a network, and the like. Various software embodiments are described interms of this exemplary computer system 500. After reading thisdescription, it will become apparent to a person skilled in the relevantart(s) how to implement the present disclosure using other computersystems and/or architectures.

The computer system 500 includes a display interface 506 that forwardsgraphics, text, and other data from the communication infrastructure 504(or from a frame buffer which is not shown in FIG. 5) for display on adisplay unit 508.

The computer system 500 further includes a main memory 510, such asrandom access memory (RAM), and may also include a secondary memory 512.The secondary memory 512 may further include, for example, a hard diskdrive 514 and/or a removable storage drive 516, representing a floppydisk drive, a magnetic tape drive, an optical disk drive, etc. Theremovable storage drive 516 reads from and/or writes to a removablestorage unit 518 in a well-known manner. The removable storage unit 518may represent a floppy disk, magnetic tape or an optical disk, and maybe read by and written on by the removable storage drive 516. As will beappreciated, the removable storage unit 518 includes a computer usablestorage medium having stored therein, computer software and/or data.

In various embodiments, the secondary memory 512 may include othersimilar devices for allowing computer programs or other instructions tobe loaded into the computer system 500. Such devices may include, forexample, a removable storage unit 520, and an interface 522. Examples ofsuch devices may include a program cartridge and cartridge interface(such as that found in video game devices), a removable memory chip(such as an erasable programmable read only memory (EPROM), orprogrammable read only memory (PROM)) and associated socket, and otherremovable storage units 520 and interfaces 522, which allow software anddata to be transferred from the removable storage unit 520 to thecomputer system 500.

The computer system 500 may further include a communication interface524. The communication interface 524 allows software and data to betransferred between the computer system 500 and external devices.Examples of the communication interface 524 include, but may not belimited to a modem, a network interface (such as an Ethernet card), acommunications port, a Personal Computer Memory Card InternationalAssociation (PCMCIA) slot and card, and the like. Software and datatransferred via the communication interface 524 are in the form of aplurality of signals, hereinafter referred to as signals 526, which maybe electronic, electromagnetic, optical or other signals capable ofbeing received by the communication interface 524. The signals 526 areprovided to the communication interface 524 via a communication path(e.g., channel) 528. The communication path 528 carries the signals 526and may be implemented using wire or cable, fiber optics, a telephoneline, a cellular link, a radio frequency (RF) link and othercommunication channels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to media such as theremovable storage drive 516, a hard disk installed in hard disk drive514, the signals 526, and the like. These computer program productsprovide software to the computer system 500. The present disclosure isdirected to such computer program products.

Computer programs (also referred to as computer control logic) arestored in the main memory 510 and/or the secondary memory 512. Computerprograms may also be received via the communication interface 504. Suchcomputer programs, when executed, enable the computer system 800 toperform the features of the present disclosure, as discussed herein. Inparticular, the computer programs, when executed, enable the processor502 to perform the features of the present disclosure. Accordingly, suchcomputer programs represent controllers of the computer system 500.

In accordance with various embodiments, where the present disclosure isimplemented using a software, the software may be stored in a computerprogram product and loaded into the computer system 500 using theremovable storage drive 516, the hard disk drive 514 or thecommunication interface 524. The control logic (software), when executedby the processor 502, causes the processor 502 to perform the functionsof the present disclosure as described herein.

In various embodiments, the present disclosure is implemented primarilyin hardware using, for example, hardware components such as applicationspecific integrated circuits (ASIC). Implementation of the hardwarestate machine so as to perform the functions described herein will beapparent to persons skilled in the relevant art(s). In variousembodiments, the present disclosure is implemented using a combinationof both the hardware and the software.

The various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope of the present disclosure.Thus, the present disclosure should not be limited by any of the abovedescribed exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

In addition, it should be understood that the figures illustrated in theattachments, which highlight the functionality and advantages of thepresent disclosure, are presented for example purposes only. Thearchitecture of the present disclosure is sufficiently flexible andconfigurable, such that it may be utilized (and navigated) in ways otherthan that shown in the accompanying figures.

The detailed description of exemplary embodiments of the presentdisclosure herein makes reference to the accompanying drawings andfigures, which show the exemplary embodiments by way of illustrationonly. While these exemplary embodiments are described in sufficientdetail to enable those skilled in the art to practice the presentdisclosure, it should be understood that other embodiments may berealized and that logical and mechanical changes may be made withoutdeparting from the spirit and scope of the present disclosure. It willbe apparent to a person skilled in the pertinent art that thisdisclosure can also be employed in a variety of other applications.Thus, the detailed description herein is presented for purposes ofillustration only and not of limitation. For example, the steps recitedin any of the method or process descriptions may be executed in anyorder and are not limited to the order presented.

The present disclosure is described herein with reference to systemarchitecture, block diagrams and flowchart illustrations of methods, andcomputer program products according to various aspects of the presentdisclosure. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flow diagramillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Elements disclosed hereinmay be implemented on a processor, such as a processor for leveragingsocial media messaging. A tangible, non-transitory memory may beconfigured to communicate with the processor. The tangible,non-transitory memory may have instructions stored thereon that, inresponse to execution by the processor, cause the processor to performoperations. Also an article of manufacture including a non-transitory,tangible computer readable storage medium may have instructions storedthereon that, in response to execution by a computer-based system, suchas a computer-based system for leveraging social media messaging, causethe computer-based system to perform operations performing functionsdescribed herein.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to effect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

We claim:
 1. A method comprising: receiving, by a computer-based system,a service request message comprising a request for transactioninformation associated with a transaction account of a merchant, a useridentification code associated with a representative of the merchant,and a transaction account code associated with the transaction accountof the merchant, wherein the transaction information includesinformation associated with at least a first location of the merchant;verifying, by the computer-based system, the transaction account of themerchant based on at least the transaction account code and the useridentification code; receiving, by the computer-based system,geo-location information of a user device that transmitted the servicerequest message; extracting, by the computer-based system, thetransaction information indicated by the request from the informationassociated with the first location of the merchant when the geo-locationinformation of the user device corresponds to the first location; andtransmitting, by the computer-based system, a reply to the servicerequest message with the extracted transaction information.
 2. Themethod of claim 1, wherein the information is associated with at leastthe first location and a second location, the method further comprisingextracting, by the computer-based system, the transaction informationindicated by the request from the information associated with the secondlocation of the merchant when the geo-location information of the userdevice corresponds to the second location.
 3. The method of claim 1,wherein service request message or the reply can be communicated with atext message, an instant message email message, multimedia messagingservice message, or short messaging service message.
 4. The method ofclaim 1, further comprising polling for new service request messagesfrom the merchant.
 5. The method of claim 1, wherein the request isrelated to a disputed transaction, a pending settlement, a transactionstatus, a chargeback, or a reconciliation.
 6. The method of claim 1,further comprising: transmitting a request for additional information inresponse to the geo-location information not corresponding to the atleast a first location, wherein the transaction information includes theinformation associated with the at least a first location of themerchant and information indicated by the additional information; andextracting the transaction information indicated by the additionalinformation.
 7. The method of claim 1, wherein the service requestmessage includes a date range for the transaction information, whereinthe reply includes the extracted transaction information that satisfiesthe date range.
 8. The method of claim 1, wherein the transactionaccount code comprises at least a portion of a transaction accountnumber for the transaction account of the merchant.
 9. The method ofclaim 1, further comprising verifying the user identification code basedon at least the geo-location information.
 10. A computer-based systemcomprising: a computing device comprising a processor and a memory; andmachine-readable instructions stored in the memory that, when executedby the processor, cause the computing device to at least: receive aservice request message comprising a request for transaction informationassociated with a transaction account of a merchant, a useridentification code associated with a representative of the merchant,and a transaction account code associated with the transaction accountof the merchant, wherein the transaction information includesinformation associated with at least a first location of the merchant;verify the transaction account of the merchant based on at least thetransaction account code and the user identification code; receivegeo-location information of a user device that transmitted the servicerequest message; extract the transaction information indicated by therequest from the information associated with the first location of themerchant when the geo-location information of the user devicecorresponds to the first location; and transmit a reply to the servicerequest message with the extracted transaction information.
 11. Thesystem of claim 10, wherein the information is associated with the atleast a first location and a second location, wherein themachine-readable instructions cause the computing device to extract thetransaction information indicated by the request from the informationassociated with the second location of the merchant when thegeo-location information of the user device corresponds to the secondlocation.
 12. The system of claim 10, wherein service request message orthe reply can be communicated with a text message, an instant messageemail message, multimedia messaging service message, or short messagingservice message.
 13. The system of claim 10, wherein themachine-readable instructions cause the computing device to poll for newservice request messages from the merchant.
 14. The system of claim 10,wherein the request is related to a disputed transaction, a pendingsettlement, a transaction status, a chargeback, or a reconciliation. 15.The system of claim 10, wherein the machine-readable instructions causethe computing device to transmit a request for additional information inresponse to the geo-location information not corresponding to the atleast a first location, wherein the extracted transaction information isindicated by the additional information.
 16. The system of claim 10,wherein the service request message includes a date range for thetransaction information, wherein the reply includes the extractedtransaction information that satisfies the date range.
 17. The system ofclaim 10, wherein the transaction account code comprises at least aportion of a transaction account number for the transaction account ofthe merchant.
 18. The system of claim 10, wherein the machine-readableinstructions cause the computing device to verify the useridentification code based on at least the geo-location information. 19.A non-transitory computer-readable medium comprising machine-readableinstructions that, when executed by a processor of a computing device,cause the computing device to at least: receive a service requestmessage comprising a request for transaction information associated witha transaction account of a merchant, a user identification codeassociated with a representative of the merchant, and a transactionaccount code associated with the transaction account of the merchant,wherein the transaction information includes information associated withat least a first location of the merchant; verify the transactionaccount of the merchant based on at least the transaction account codeand the user identification code; receive geo-location information of auser device that transmitted the service request message; extract thetransaction information indicated by the request from the informationassociated with the first location of the merchant when the geo-locationinformation of the user device corresponds to the first location; andtransmit a reply to the service request message with the extractedtransaction information.
 20. The non-transitory computer-readable mediumof claim 19, wherein the machine-readable instructions, when executed bythe processor, further cause the computing device to at least: transmita request for additional information in response to the geo-locationinformation not corresponding to the at least a first location, whereinthe transaction information includes the information associated with theat least a first location of the merchant and information indicated bythe additional information; and extract the transaction informationindicated by the additional information.